Skip to content

Conversation

@awilfox
Copy link
Member

@awilfox awilfox commented Jan 23, 2026

Since we have two dropdowns with the same name, their values will both be sent on requests. The sandbox dropdown is last, so its value will take precedence over the production list. By having an empty item as the first item, the value will be blank and the selected item in the production list will be used.

Closes: AP-560


I was obviously unable to test this (as I didn't want to set any notes on Alma item sets), but stubbing out the request logic locally seemed to do the right thing. We should probably have someone in Collections test this in staging before pushing to production.

Copy link
Member

@anarchivist anarchivist left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

r+, minor nit re: making the purpose of this change explicit.

Since we have two dropdowns with the same name, their values will both
be sent on requests.  The sandbox dropdown is last, so its value will
take precedence over the production list.  By having an empty item as
the first item, the value will be blank and the selected item in the
production list will be used.

Closes: AP-560
@awilfox
Copy link
Member Author

awilfox commented Jan 24, 2026

v2: Moved assignment to the top of the method and added a comment about why we start with an empty element in the list.

@awilfox awilfox requested a review from anarchivist January 24, 2026 17:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants